Network personal digital video recorder system

ABSTRACT

The Shared Internet Storage Resource provides Internet-based file storage, retrieval, access, control, and manipulation for a user. Additionally, an easy-to-use user interface is provided both for a browser or stand-alone application. The entire method provides means by which users can establish, use, and maintain files on the Internet in a manner remote from their local computers yet in a manner that is similar to the file manipulation used on their local computers. A high capacity or other storage system is attached to the Internet via an optional internal network that also serves to generate and direct metadata regarding the stored files. A web server using a CGI, Java®-based, or other interface transmits and retrieves TCP/IP packets or other Internet information through a load balancer/firewall by using XML to wrap the data packets. File instructions may be transmitted over the Internet to the Shared Resource System. The user&#39;s account may be password protected so that only the user may access his or her files. On the user&#39;s side, a stand-alone client application or JavaScript object interpreted through a browser provide two means by which the XML or other markup language data stream may be received and put to use by the user. Internet-to-Internet file transfers may be effected by directly downloading to the user&#39;s account space.

CROSS-REFERENCES TO RELATED APPLICATIONS

This patent application is a continuation of U.S. patent applicationSer. No. 11/075,311 filed Mar. 8, 2005 for Shared Internet StorageResource, User Interface System, and Method, a continuation of U.S.patent application Ser. No. 11/089,173 filed Mar. 23, 2005 for SharedInternet Storage Resource, User Interface System, and Method, acontinuation of U.S. patent application Ser. No. 11/089,174 filed Mar.24, 2005 for Shared Internet Storage Resource, User Interface System,and Method, and a continuation of U.S. patent application Ser. No.11/089,397 filed Mar. 24, 2005 for Shared Internet Storage Resource,User Interface System, and Method.

U.S. patent application Ser. No. 11/075,311 filed Mar. 8, 2005 forShared Internet Storage Resource, User Interface System, and Method andU.S. patent application Ser. No. 11/089,173 filed Mar. 23, 2005 forShared Internet Storage Resource, User Interface System, and Method aredivisional applications of U.S. patent application Ser. No. 10/073,775filed Feb. 11, 2002 entitled Shared Internet Storage Resource, UserInterface System, and Method which issued as U.S. Pat. No. 6,985,927 onJan. 10, 2006.

U.S. patent application Ser. No. 11/089,174 filed Mar. 24, 2005 forShared Internet Storage Resource, User Interface System, and Method, andU.S. patent application Ser. No. 11/089,397 filed Mar. 24, 2005 forShared Internet Storage Resource, User Interface System, and Method arecontinuation-in-part applications of U.S. patent application Ser. No.10/073,775 filed Feb. 11, 2002 entitled Shared Internet StorageResource, User Interface System, and Method which issued as U.S. Pat.No. 6,985,927 on Jan. 10, 2006.

U.S. patent application Ser. No. 10/073,775 filed Feb. 11, 2002 entitledShared Internet Storage Resource, User Interface System, and Methodwhich issued as U.S. Pat. No. 6,985,927 on Jan. 10, 2006 is acontinuation of U.S. patent application Ser. No. 09/570,583 filed May12, 2000 for a Shared Internet Storage Resource, User Interface System,and Method which issued as U.S. Pat. No. 6,351,776 on Feb. 26, 2002which is related to U.S. Provisional Patent Application No. 60/163,626filed Nov. 4, 1999 entitled Shared Internet Storage Resource, UserInterface System, and Method which applications are incorporated hereinby this reference thereto.

This patent application is related to and claims priority from U.S.Provisional Patent Application No. 60/163,626 filed Nov. 4, 1999entitled Shared Internet Storage Resource, User Interface System, andMethod which application is incorporated herein by this referencethereto.

All of the aforementioned patents and patent applications as well as anyother related patents and/or patent applications are incorporated hereinby this reference thereto.

BACKGROUND OF THE INVENTION Field of the Invention

This invention relates to resources on computer networks, particularlythe Internet, and more particularly to a file storage and retrievalsystem that is available worldwide via the Internet which additionallyallows a direct transfer of Internet files to an Internet storage,retrieval, and sharing resource. The present invention acts in themanner of a “Internet hard disk” or “Internet hard drive” to provideonline storage and retrieval resources for users.

Description of the Related Art

The Internet is the worldwide computer network making available a vastnumber of computer and information resources to institutions andindividuals. A significant part of the Internet is the worldwide webthat allows for web pages to be written in HTML and transmitted upondemand throughout the Internet. Recent developments have betterestablished the use of XML (Extensible Markup Language) as a subset ofSGML (Standard Generalized Markup Language, ISO standard 8879:1986). FTP(File Transfer Protocol) provides means by which files may betransferred over the Internet. All of these protocols are generally wellknown in the art, and collateral resources can easily be obtained todescribe these further.

Additionally, portable programming systems such as Java®, JavaBeans, andJavaScript have been extensively developed with an anticipation offuture portability across the vast network that is the Internet.Java®-related systems allow for object-oriented programming wherebyobjects or “beans” allow the passing of self-contained modules withassociated processing methods that are used to act upon the accompanyingdata. Consequently, the “bean” can travel through a network and, underappropriate circumstances, have certain processes activated allowingmanipulation of the information contained in the bean.

Advancements in Java®-related systems have given rise to the EnterpriseJavaBean™ (EJB). The Enterprise JavaBean™ allows for clustering ofservers such that the bean is given independence from specific serverson the system, yet can be activated or “instantiated” such that errorrecovery is easier, the system as a whole is more robust, and processingof the bean can be performed asynchronously so that all events do nothave to happen at a pre-set time or serially/one after the other.

Enterprise JavaBeans™/EJBs allow serialization of beans. Suchserialization allows the bean to be represented as a data stream ofdetermined length. In essence, this is just a data file that isinterpreted in the proper context, much the same as any electronicinformation file. Such serialization of the EJB allows it to bereplicated and stored in case of catastrophic failure of a preferredserver or the like.

If the server upon which the instantiated EJB dies, goes down, or fails,a previously replicated twin can be used to continue the process andallow for error recovery. More information about Enterprise JavaBeans™technology can be found in the white paper, “Enterprise JavaBeans™Technology: Server Component Model for the Java™ Platform” by AnneThomas, revised December 1998, prepared for Sun Microsystems, Inc. andpublished/made available by the Patricia Seybold Group of Boston, Mass.

Due to the nature of new technologies, terms such as “bean” or“instantiated” may seem unfamiliar to those new to the pertinent art.Reasons for this include the difficulty of communicating quickly new andcomplex subjects as well as the good-humored nature of those whointensely pursue the establishment of new technology, particularlysoftware systems. Consequently, for Java®-related systems, a coffeetheme is often present that indicates to those knowledgeable in the artthe general subject matter of interest. While distinctions may be subtlein the art, they can be very important and serve the ends of thoseattempting to establish, share, and forward the technology.

Generally, home pages or other web pages are requested by the userthrough designation of the URL (Uniform Resource Locator). With thetransmission to the user via TCP/IP protocol, the information present atthe URL (and generally a file located somewhere on a computer) istransmitted to the user. The file may have links, or pointers, to otherresources including images, graphics, audio or video streams, or otherresources. Mark-up language is used on the Internet in an attempt toprovide an open-ended structure by which information of any sort thatcan be stored electronically (or perhaps even otherwise) can be madeavailable to an end user on demand. As such, the Internet is seen as apowerful tool making almost any information resource available to anycomputer or to any person using a computer.

Over the past several years, the personal computer has increased inpower and capacity as commercial demand has driven the research anddevelopment of producers and vendors. It is now not uncommon to be ableto easily find an Intel-manufactured 500 megahertz Pentium®-based systemhaving well over 10 gigabytes of hard disk space, as well as 32-256megabytes of RAM. As such, the power by which files may be received andacted upon by the local user through his or her PC has kept pace withthe advances in technology.

However, there currently remain obstacles to universal access to anindividual's own information stored on his or her computer. First ofall, computers are very heavy. They are bulky. They generally weighseveral kilograms and are not easily transportable. Lightweight laptopcomputers or the like generally do not have the same resources availableto the user as a regular PC. Additionally, access to local area networks(LANs) is generally not available once the computer leaves the premisesoccupied by the LAN. Additionally, Internet access is often restrictedby the use of a modem. Modems generally provide data transmission speedson the order of 56 kilobits per second. This is approximately the sameas 7 kilobytes per second. However, headers and other information arerequired to properly transmit information over the Internet and increasethe effective size of files.

Even with the increased availability of broad band access to theInternet, it becomes an important feature of electronic informationprocessing and the like in order to provide resident resources on theInternet. Such resources could include the sharing of files and the likein a manner that are easy to use and understand.

Due to these and other restrictions regarding data transport,transmission, and reception, a need has arisen for means by which filesand other data may be available worldwide through the Internet and nottied to a local computer. The present invention addresses this demand byproviding means by which files and other data may be stored on theInternet and made available worldwide through the Internet.

SUMMARY OF THE INVENTION

The present invention provides an “Internet hard drive” or “Internethard disk” to and from which files may be stored and retrieved.Denominated commercially as “X:Drive,” the present invention allowsusers to store files of foreseeably any type on a resource availablethroughout the Internet. Once available to the Internet, the filesstored on the user's X:Drive are available to the same extent as theInternet, namely worldwide.

Note should be made that the term “X:Drive” refers both to the system asa whole and to the individual space allocated to an individual user.Consequently, reference is sometimes made herein to the X:Drive systemor to X:Drive to refer to the system as a whole. At other times, theterm X:Drive indicates the user's individual X:Drive, or allocatedspace. The different uses are indicated by context.

In order to effect the Shared Internet Storage Resource of the presentinvention, a central or distributed storage facility is provided. Firstand foremost is the high-speed access storage facility where files areactually stored. Such individual storage areas may be allocated inindividual limited allotments, or be left open-ended and limited only bythe capacity of the physical devices responsible for storage. Metadata,that is data about the files stored on the network hard drives or otherstorage devices, is generated and stored in a separate database. Thedatabase of metadata (the metadatabase) and the network-attached storagefacility may be linked by an internal network. It is possible for thedatabase to be stored on the same network storage facility or device onwhich user files are also stored. System management may select whetheror not to distribute or consolidate the database with the networkstorage.

Also attached to the internal network is a web server that serves togenerate and transmit the information to the Internet, and ultimatelythe user. The web server files may pass through a load balancer and/orfirewall before proceeding on to the Internet. The same is similarlytrue for information coming into the web server from the Internet.

XML may be used in combination with JavaScript or the like to providetwo means by which the Shared Internet Storage Resource of the presentinvention may be achieved. The first is a JavaScript object which may betransmitted to a browser program running on the user's computer. Suchbrowsers may include ones that are well known, including Netscape®Communicator and Microsoft® Internet Explorer. Alternatively, astand-alone application may be installed and stored upon the user'scomputer. This stand-alone application serves to intermediate the usercommands with the web server and ultimately the metadatabase in theInternet storage device.

As an additional enhancement, the user interface may be a client programthat meshes seamlessly with standard user presentations in WYSIWYG (whatyou see is what you get) graphic user interfaces (GUIs). As such, adrive may be shown on the user's computer and may be denominated “x:”(or “y:” or “z:”, etc., depending upon user preferences). The user canthen read from or write to the x:\ Shared Internet Storage Resourcedrive much in the same way as you would the local a:\ and c:\ harddrive.

When the user shuts down his or her computer, information that is storedon the Shared Internet Storage Resource of the present invention remainson the Internet. The user can then access such information from anothercomputer, another geographic location, or even give permission to sharefiles on the Shared Internet Storage Resource with others. Passwordprotection or other security protocols may be used to limit ordiscriminate access to the user's files.

The Shared Internet Storage Resource of the present invention allows fordirect Internet-to-Internet file transfer to a user's allocated X:Drivefile space in a process referred to as “Skip the Download” or “Save toMy Xdrive.”

OBJECTS OF THE INVENTION

It is an object of the present invention to provide a Shared InternetStorage Resource on which users may store and retrieve files to makethem available to themselves, or possibly others, throughout theInternet.

It is an additional object of the present invention to provide allmanner of file access and control generally available to files local tothe users for such Internet-stored files.

It is an additional object of the present invention to provide aneasy-to-use and readily understood user interface through which filesmay be stored, retrieved, and manipulated on the Internet.

It is an additional object of the present invention to gather metadataregarding such files and to store such metadata in a database.

It is yet another object of the present invention to provide a pluralityof means by which Internet-stored files may be manipulated andcontrolled.

It is yet another object of the present invention to provide abrowser-based access to Internet-stored files.

It is yet another object of the present invention to provide stand-aloneapplication access Internet-stored files.

It is yet another object of the present invention to provide means bywhich Internet files may be stored on an Internet resource by a directInternet-to-Internet transfer subject to the control of a remote orlimited-resource user.

These and other objects and advantages of the present invention will beapparent from a review of the following specification and accompanyingdrawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic view of the X:Drive system of the presentinvention. The different tier levels are shown, along with the markingindicia of a circle, triangle, square, and star/asterisk correspondingto the same indicia in FIGS. 3A and 3B.

FIG. 2 is a schematic view of Java® library objects operating in thetransactions or data exchanges occurring in the present invention.

FIGS. 3A and 3B are detailed flow diagrams showing the operation of thepresent invention. Indicia including a circle, a triangle, a square, anda star/asterisk correspond to tier levels shown in FIG. 1 and indicatethe level of operation of the steps shown in the flowchart of FIGS. 3Aand 3B.

FIG. 4 is a flowchart showing the operation of the XDFile EnterpriseJavaBean™ (EJB) used in the present invention.

FIG. 5 is an overview of the Java® architecture used to effecttransactions in the present invention.

FIG. 6 is an alternative schematic diagram of the Java® architectureshown in FIG. 5.

FIG. 7 is a schematic and flowchart diagram showing the IO(input/output) for the database transactions of the present invention.

FIG. 8 is a schematic diagram of the data recovery process as effectedby the FileIO component of the XDFile object used in the presentinvention.

FIG. 9 is a schematic depiction of failure recovery elements.

FIG. 10 is a schematic and flowchart diagram showing virus protectioneffected in the present invention.

FIG. 11 is a schematic and flowchart diagram of the Internet-to-resourcetransfer (“Skip the Download”/“Save to My Xdrive”) as set forth in thepresent invention.

FIG. 12 is a schematic and flowchart diagram of the client system usedin the present invention.

FIG. 13 is a Windows™ desktop display showing both the client andweb-browser applications.

FIG. 14 is a display of a web browser pointing to a user's X:Drive.

BRIEF DESCRIPTION OF THE APPENDICES

Appendix 1 is a listing of web site/server code use to achieve thepresent invention.

Appendix 2 is a listing of the code used on the client side to achievethe present invention in a Microsoft® Windows™ environment.

Appendix 3 is a listing of the JavaScript code used to achieve thepresent invention in a la Sun Microsystems® Java® environment (includingone on a browser).

DESCRIPTION OF THE PREFERRED EMBODIMENT(S)

The detailed description set forth below in connection with the appendeddrawings is intended as a description of presently-preferred embodimentsof the invention and is not intended to represent the only forms inwhich the present invention may be constructed and/or utilized. Thedescription sets forth the functions and the sequence of steps forconstructing and operating the invention in connection with theillustrated embodiments. However, it is to be understood that the sameor equivalent functions and sequences may be accomplished by differentembodiments that are also intended to be encompassed within the spiritand scope of the invention.

Appendices 1, 2, and 3 provide the source code for, respectively, theWeb Site/Server Code of the X:Drive Shared Internet Storage Resourcesystem of the present invention; the Windows Client Code; and theJavaScript Listings for the present invention. These Appendices areincorporated herein by this reference thereto as if set out in theirentirety.

Additionally, the reference numbers used in conjunction with the figuresare numbered such that the 100's place of the number indicates thenumber of the drawing figure. For example, the 600 series of referencenumbers refers to FIG. 6, while the 200 series refers to elements shownin FIG. 2.

The present invention provides a method by which an Internet hard diskor hard drive may be achieved in a manner similar to a hard disk or harddrive available locally to the individual on the local computer.Additionally, as Internet use becomes a more familiar and everyday eventfor people, the resources provided by the present invention may allowthe actual use of the Internet hard drive or X:Drive set forth herein toact as such a resource with the files being called up for execution forprograms available and processed either locally and/or over theInternet. In light of the foregoing, it can be seen that the presentinvention may act as a bridge or may pave the way towards a moreinter-networked community for the use and processing of electronicinformation.

The virtual disk drive provided by the present invention may beselectively shared with others or kept entirely private. Additionally,and as set forth in more detail below, the use of a metadatabaseprovides quicker access and the ability distribute the informationregarding the legion of X:Drive accounts over a wide geographic area,enabling redundant preservation of user information by server clustersimplementing Enterprise JavaBeans® (EJBs), or otherwise.

The Shared Internet Storage Resource, User Interface System, and Methodset forth herein is generally referred to as “X:Drive.” Context revealswhether or not the term X:Drive is referring either to the system as awhole or the individual's own account.

The X:Drive system of the present invention uses network applicationpractices and may rely upon Java® Enterprise JavaBeans™ (EJBs) to enabledistributed and clustered computing and file management environment.Along with such Java®-based and network-oriented design, the X:Drivesystem of the present invention also contemplates the use of openprogramming standards such as XML and Web-DAV (Web-based DistributedAuthoring and Versioning). The use of such technology is foreseen asproviding wide support by the user community as well as speed anddevelopment, refinement, and polishing.

As shown in FIG. 1, the X:Drive system 100 has a multi-tiered,network-based application infrastructure. The multi-tiered nature of thesystem allows it to separate operations in an efficient manner. Thenetwork-based aspects of the X:Drive system allows it to disperseresources geographically as well as allow a high degree of communicationbetween different aspects or facets of the system.

The X:Drive system may be considered enabling technology as a mediumthat is independent of the applications and uses to which it is applied.The X:Drive system is currently based on object-oriented principles witheach application layer responsible for a discreet functionality oraspect of operation. Both hardware and software resources may thensuccessfully experience heavy re-use with both scalability andflexibility inherently provided. While these advantageous aspects of theX:Drive system are achieved, as a multi-tiered system, X:Drive involvesa higher cost of complexity and planning. Thus, those who would seek towrongly copy the X:Drive system would do so without accruing the greatexpense in time and money necessary to achieve the present X:Drivesystem. They would ride on the backs of those who not only developed thesystem, but also those who got it to work right and in acommercially-reliable manner.

The use of tiers in the X:Drive system of the present invention isrealized in both the network systems and the application systemsinvolved in achieving X:Drive.

As shown in FIG. 1, a variety of tiers, or layers, are present betweenthe client 102 and the ultimate data resources 104. Between the client102 and the data resources 104, are one or more layers or tiers,accomplishing the following.

The client 102 may be coupled to a public network 106 (such as theInternet) that may include a DNS redirector 108 as well as a loadbalancer 110. The public network 106 may then lead into a web servernetwork 120. The web server may then lead into an application a network122, which in turn leads into an EJB (Enterprise JavaBeans™) network124. The EJB network 124 may lead into a transaction network 126, whichin turn leads into the data resources 104.

The client 102 may be either a web- or browser-based application or anapplication resident on a Windows™ X system (the X indicating theversion of Windows applicable, i.e., Windows® 95, Windows® 98, Windows®2000, etc.). Requests generally originate from the client as the X:Drivesystem 100 is one that operates at the command of users directing theclient program. Client requests may be made versus the HypertextTransfer Protocol (HTTP) GET/POST function. In a preferred embodiment,the GET/POST operation may be augmented with Web-DAV extensions to theHTTP protocol. Commands are transmitted by the client 102 are sent tothe DNS redirector 108, which then isolate the request via a proxyserver process. A proxy server process prevents a direct connectionbetween the client 102 and the other downstream resources in the X:Drivesystem 100. Such proxy serving prevents inadvertent or mischievousdisruption of service by allowing only certain commands or informationto be propagated through the X:Drive system 100. This preventsmischievous users from disrupting the system as such rogue commands areintercepted by the proxy server and denied further propagation.

After the client command has passed through the DNS redirector/proxyserver 108, the request by the client 102 is then directed to the mostappropriate facility. As the X:Drive system is scalable, facilities maybe distributed geographically, even over the face of the globe. Thisallows, at the outset, more efficiencies to take place in the X:Drivesystem 100 of the present invention so that more users may be servedmore quickly and so that the advantageous features of the X:Drive systemmay be realized by the widest number of users in the quickest waypossible.

Due to the construction and architecture of the X:Drive system 100, anumber of machines/servers running a number of different processes maybe distributed over a wide area. Broad band or high-speed access asprovided by Internet backbone or the like may allow the X:Drive systemto be effectively carried out over the entire face of the planet. Thescalability and flexibility of the present invention augments itsutility. Such advantages are further advanced by efficient use of theresources so that greater and better service can be provided.

Upon receiving the request from the client 102, the DNS redirector 108transmits the requests on to a load balancer which may provide a secondproxy process under HTTP protocol and transmit the request to theleast-loaded and most-available web server on an internal, non-mutable,or other server network 120.

The web server network 120 may be non-routable and may comprise a numberof individual machines or servers processing the HTTP or other requestsfrom one or more load balancers 110. Each of the web servers 140 in thenetwork 120 may handle HTTP requests for static content, such as HTMLand graphic files. The web servers may proxy all requests for dynamiccontent to a Java® application network 122.

As used in the X:Drive system 100 of the present invention, the Java®application networks may be non-routable. The use of non-routablefacilities in the X:Drive system 100 of the present invention indicatestheir operation in a local area network (LAN). However, between tiers,the individual networks themselves may be available such that a webserver 140 in Illinois may pass requests for dynamic content to Java®application clusters 122 in Wisconsin.

Each Java® application cluster 122 may be composed of a number of Java®application servers 142 with each server 142 handling display functionsnecessary for user accounts, including the generation of XML, HTML, andother instructing displays for either browser or application clients102. If a Java® application cluster 122 receives a resource request fromthe web server tier 120, the Java® application cluster 122 will pass theresource request onto the Enterprise JavaBean™ EJB network tier 124.

As for the web server 120 and Java® application networks 122, the EJBnetwork 124 may also be non-routable and operate upon a LAN. The EJBnetwork may be an EJB cluster having a number of EJB servers 144. EachEJB cluster handles the business logic and resource access methods andprotocols required for the resource requests and management. The EJBcluster (EJBC) caches memory of common resources such as the pooling ofdata connections and the like, as well as data objects. Resource accessrequests and transmissions are then passed out to the transactionnetwork tier 126, which may also be non-routable. The transactionnetwork tier 126 has a transaction processor 146 which controls,operates, and guarantees access and transactions on different resources.These different resources are the ultimate data resources 104 that mayinclude NFS (Network File Server) disk arrays 150 and databases 152. TheNFS disk arrays 150 may supply the actual storage capacity for the filesof generally any size. The databases 152 comprise records of informationregarding each of the files (metadata) stored by the NFS disk arrays 150under the X:Drive system 100.

By bifurcating the file information in databases 152 separate from theactual files themselves on the NFS disk arrays 150, file information anduser queries can be handled much more quickly as display components ofthe present invention are important to provide the user informationregarding the status and availability of the files stored on the X:Drivesystem 100. Consequently, although a user may have a hundred separatefiles in an X:Drive directory, he or she may be only interested in one.Consequently in order to provide the user the information necessary tomake the decision as to which file to receive, move, rename, delete, orstore, the use of the database provides a very quick and easy means bywhich such user requests can be satisfied. It is anticipated that theactual use of the file storage facilities on the NFS disk arrays 150 orthe like may comprise only a part of the operations of the presentinvention. Having the ability to display, select, and determine fileoperations is one of the useful advantages provided by the X:Drivesystem 100 of the present invention.

Note should be taken of the non-numerical indicia present in FIG. 1.Most notably, a circle is associated with the client 102, a trianglewith the Java® application cluster 122, a square with the EJB network124, and a star/asterisk with the transaction network. Thesenon-numerical indicia correspond to those set forth in FIGS. 3A and 3B.As different actions are performed at different tiers in the presentinvention, the non-numerical indicia provide an easy or visual means bywhich the operation of the different tiers can be indicated in FIGS. 3Aand 3B.

FIG. 2 shows a logic diagram in sequence structure for the Java® libraryobjects used in the X:Drive system 100 of the present invention.Generally, throughout the description of the X:Drive system 100 of thepresent invention, the prefix XD indicates “X:Drive.” For example, inFIG. 2 the steps/status indicators of XDError stands for X:Drive Error,and XDXML stands for X:Drive Extensible Markup Language. Likewise, theuse of the term XDFile indicates X:Drive File as a Java® library objecteffecting and intermediating the file operations of the presentinvention.

In FIG. 2, the Java® system 200 allows operations to be performed on themetadatabase 202 and the operating system (OS) File System 204.Additionally, the XDFile object 210 may activate or instantiate theDatabase.Search object 216. The XDFile object 210 may be activated, orinvoked, by the FileAction object 220. The FileAction object 220 mayalso activate the Database.Search 216 and Database.BigSearch 222objects. Operations of the Java® library objects in the system 200 asshown in FIG. 2 may be contingent upon the SessionSecurity object 224,which may instantiate or use the Database.Search object 216 and/or theDatabase.Transaction object 214. The SessionSecurity object 224 mayreturn a separate object 226 to the UserData object 230. The Databaseobject 236 may inherit or transmit from its Transaction 214, Search 216,and/or BigSearch 222 objects.

The information generated may then be transmitted to the Database 202for meta-information and the OS File System 204 for the actual data. Ifan error is generated during the operation of the Java® library objectsystem 200, an XDError object 240 may serve to handle the error while asuccessful operation may be returned in the form of the XDXML object242. In the Java® library object system 200 of FIG. 2, the Database 202may contain intelligence or programming for connection to SQL databasesand the like. Options regarding the operations of the database 202 maybe read from a configuration file. The Database object 236 may be ableto connect multiple databases for redundancy in the case of repeated orredundantly archived information, or for functionality in order toconnect to that database which responds most quickly to the requests andcommands.

The Database object 236 determines which database operation to performand/or to which database to send operations based on the type of requestit receives. For example, transaction requests may demand a separatedatabase from those of regular query and BigSearch 222 requests. Inorder to maintain more efficient operation, the Database object 236generally sends session users to the same database whenever possible sothat latency and database replication is not passed on to the user.

The Database.Transaction object 214 is able to handle larger SQLstatements such as those that would cause a load on the database. TheDatabase.Transaction object 214 may spawn children classes that handlethe transaction logic in order for more efficient operation.

The Database.Search object 216 is designed to handle smaller SQLstatements and has children classes for specific search types, such asthose along anticipated and common fields or types of information.

The Database. BigSearch object 222 handles larger, non-transactional SQLstatements such as those used for reports in system accounting,monitoring, or otherwise. Children classes of the Database.BigSearchobject 222 would handle specific large searches such as those that mightbe implemented on a monthly or other periodic basis.

The FileIO object 212 inherits and overrides Java®'s data file object.The file object contains logic to engage multiple disks or resources forredundancy and/or functionality and contains the functionalitiesnecessary to manipulate files on the OS File System 204. The FileIOobject 212 may react to the JMS (Java Messaging Service) eventstriggered by events on the disks of the OS File System 204.

Alternatively, one or more monitoring objects may be used to gatherpertinent status information regarding the OS File System 204. Whenmonitoring objects are used, the FileIO objects then query the commonmonitoring objects to determine the state of the system. In the presentsystem, the monitoring object is denominated the Mount Point Statusbean, or MPS bean, 534 (FIGS. 5 and 9).

Additionally, disk level transactions are carried out by the FileIOobject 212. Under the management of the FileIO object 212, user accountsare able to span or traverse several disks. The spanning of such severaldisks enables better recovery from failure should an error occur orsystem resources become unavailable in an unpredictable manner. TheXDFile object 210 uses FileIO 212 to handle the file systemtransactions. By using the Database.Transaction file object, the XDFileobject 210 handles database file transactions. The XDFile object 210coordinates transactions for both the FileIO object 212 and theDatabase.Transaction file object 214 to keep both synchronized and tohandle failure should it occur.

The UserData object 230 holds user data for a session of the X:Drivesystem. A session is basically a span of time for which a user engagesthe X:Drive system. Methods are included in the UserData object 230 tomanipulate the user status, so that the activity may be monitored, aswell as whether or not the user has logged in.

The SessionSecurity object 224 uses web logic session mechanisms tocreate the UserData object 230. It does this by returning a separateobject 226. The SessionSecurity object 224 authenticates a user's loginand expires old sessions with re-direction of such old sessions toappropriate pages.

The FileAction object 220 may have children classes and contain logicfor determining request types such as user requests, administrationrequests, etc. Tests for file action requests such as quotas andpermissions, etc., May also be handled by the FileAction object 220. TheFileAction object 220 accesses the file methods in the XDFile object210.

The XDError object 240 reads a configuration file of error lists whichgives each error number. Such error lists preferably pivot on thelanguage in which the X:Drive system 100 of the present invention isprogrammed. Such lists should also be able to pivot on the partner withwhich the X:Drive system 100 operates, Default values for the lists maybe to X:Drive errors in the English language. The XDError object 240preferably holds errors in a stack and returns any such errors from thestack. Additionally, the XDError object 240 preferably accepts newerrors by code or by message.

The XDXML object 242 accepts an object and delivers as output an XMLrepresentation of a transaction or status requested by the user orclient software.

FIGS. 3A and 3B show the data flow through the X:Drive system 100 of thepresent invention, particularly that as reflected by the tieredconfiguration shown in FIG. 1. From a starting point 300, a request issent by HTTP POST/GET command at step 302. Web-DAV protocol may also beused and is currently considered preferable. The send request isimplemented on the client 102 and is evaluated by the web server 120 asa request for static content in step 304. If the request is for staticcontent, the file is served by the web server 120 at step 306, and thefile is displayed at step 308 by the client 102.

If at step 304 the request for static content is evaluated as negative,a proxy request is issued by the web server network 120 to the Java®application cluster 122 at step 312. The request is received by theJava® application cluster (JAC) 122 and submitted to a servlet at step314. The Java® application cluster (JAC) 122 then parses the requestheader at step 316. The Enterprise JavaBean™ (EJB) network 124 thenauthenticates the request at step 318. If authentication cannot beachieved, process control is then re-directed to the re-login page viathe JAC network 122 at step 320. If authentication succeeds at step 318,the JAC network 122 then parses the multi-part form data at step 324.

The JAC network 122 then determines the type of request at step 326. Therequest is then submitted to the FileAction EJB 220 at step 328. The EJBnetwork 124 then evaluates the request at step 330 in order to ensurethat all the business rules and other applicable limitations are met,such as quota limitations, permissions, and the like. If the evaluationis successful at step 330, the EJB network 124 then submits the requestto the XDFile EJB 210 at step 332 and on to the transaction processor146. The appropriate actions are then taken via the transactionaldatabase 152 and the disk arrays 150. If the business rule evaluation330 fails, an error may be generated and, as for other errors in thedata flow process of FIGS. 3A and 3B, a session error object 334 may begenerated in a session error stack 336.

In effecting the data transfer to the ultimate system resources 104,evaluation is made as to the operation in step 340. If the operation isnot a data read operation such as a directory listing or file read, theerror stack is checked at step 342. If an error has occurred, the errorstatus is sent to the client 102 at step 344. The client 102 thenaccepts the transmitted XML code and renders the appropriate display forthe user at step 346. If the error stack evaluation step 342 does notreveal any error, a success message is generated at step 350, and thesubsequently-generated XML is received by the client 102 and displayedby the user at step 346.

If at the evaluation step 340, the operation is not a data read action,the error stack is checked at step 352 much in the same way as it was atstep 342. If an error has occurred, the error status is sent to theclient 102 at step 354. The error status message is then received as XMLcode by the client 102 at step 346 and displayed to the user. If atevaluation step 352 the error stack reveals no errors, the evaluation isthen made by the EJB cluster as to whether or not the operation is afile read at step 360. If the operation is a file read, the data streamis converted to a network stream and transmitted as a file to the client102 by the Java® application network 122 at step 362. The data is thenaccepted by the client 102 and served to the user at step 364.

If at evaluation step 360 the operation is not a file read (see FIG. 4),then by elimination, the action is a request for file metadata such as adirectory listing indication of file attributes or the like. At step366, the metadata retrieved from the database 152 is then translatedinto XML format by the EJB cluster 124. The XML data is then transmittedto the JAC network 122, which encapsulates the XML from the network andsends it on to the client at step 368. The JAC network 122 then sendsthe encapsulated XML to the client 102 for rendering and display at step346.

As indicated in the description above with regards to FIGS. 3A and 3B,users utilizing the client system 102 to connect to the X:Drive system100 do so via the public Internet and then submit requests and receivereplies effecting or indicating the user's requests. Requests for filemanipulations, such as uploads, downloads, copies, moves and updatestravel through each functional layer of the X:Drive system 100.

The core of the EJB cluster, and as indicated in FIG. 2, the XDFile EJBprovides core effectiveness in the present X:Drive system 100. TheXDFile EJB 210 is a multi-tiered component. The X:Drive system 100stores file metadata (such as directory structure, file name, fileattributes, etc.) in the database 152 for fast retrieval, sorting,searching, linking, and other capabilities beyond standard file systems.The actual file data is stored by the X:Drive system 100 innetwork-attached storage units or storage area networks such as thoseshown in FIG. 1, the NFS disk arrays 150.

To access files that exist in this hybrid environment (bifurcatedbetween file s information and file data), X:Drive uses the XDFileobject 210 to manipulate both files and file data in two-phase committaltransactions. FIG. 4 shows the details of these transactions.

In FIG. 4, the XDFile EJB system 400 allows entry at any one of the fivedarkened triangles. If the action is to be a copy, entry is made at thecopy entry point 402. If the action is a file read, entry is made at thefile read point 404. If the action is a file write, entry is made at thefile write point 406. If the action is a file delete, entry is made atthe delete point 408. If the action is a file move, entry into theXDFile EJB 210 is at the move entry point 410.

Beginning first with a file copy action beginning at the copy point 402,the evaluation of the operation occurs at step 420, where determinationis made whether or not the action is a read transaction. If the actionis a read transaction, program flow proceeds onto the read action andentry point 404. The corresponding database action 424 is then taken. Asthe action is a read transaction, the corresponding database record isread and evaluation is made as to whether or not the database action, inthis case read action, has been successful at step 428. If the readaction is not successful, the changes are then rolled back, if any, atstep 432. An error is then returned at step 436 and the XDFile objectawaits further instructions. If the evaluation at step 428 regarding thedatabase action was successful, action can then be taken on the actualfile itself on the OS File System 204 at step 440. In the present case,the FileOS Action 440 is a read action, and the file may be read into atemporary buffer or other memory space. The FileOS Action is evaluatedfor success at step 444. If the FileOS Action step 440 was unsuccessful,a fatal error is returned at step 448, and the changes, if any, arerolled back at step 452. If the evaluation at step 444 was successful,evaluation is made as to whether or not the action was a copy read atstep 456. If the action was a copy read, return is made to the copyentry point 402 at step 464 in order to perform the write portion of thecopy function. If the evaluation at step 456 indicates that the actionwas not a copy read action, evaluation is made at step 468 to determineif the action was a move/copy action. If the action was a move/copyaction, control is then directed towards the move entry point 410 viastep 472 in order to delete the original file as the success of themove/copy transaction at evaluation step 444 indicates the success ofthe file write step of the FileOS Action step 440. Program control isthen turned over to the move/action entry point 410 so that the originalfile may be deleted at its original location via the delete entry point408.

If the move/copy evaluation step 468 indicates that not only was theaction not a copy read, it was also not a move/copy, then the action iscommitted to the system at the ultimate system resource level 104 atstep 480 and an indication of success is then returned at step 484.

Upon reaching the move entry point at 410, evaluation is made at step490 to determine whether or not the transaction is a copy transaction.If it is a copy transaction, the program then enters and executes thecopy entry point 402. If not, the delete entry point 408 is activated toeffect the remainder of the move transaction.

Consequently, it can be seen that a variety of actions take placedepending upon the state of the XDFile EJB 210 at the database action424 and FileOS action 440 steps.

In performing file reads and writes, simple one-step actions are takenbecause neither of these read or write actions are either copy reads 456or move/copy 468 and so they fall into the system commit 480 and returna successful indication at step 484. The same is generally true for theone-step delete action. Consequently, whenever a user wants to read,write or delete a file, entry can be made into the respective entrypoints at 404, 406, and 408. Errors are returned when necessary.

However, the copy action 402 and the move action 410 require multipleloops through the XDFile EJB 210 in order to effect their operations.For the copy function 402, the initial read must be made successfullywith the evaluation step 456 then prompting the write step to occur bythe return to the copy entry point at step 464. The read transactionstep 420 is then evaluated in the negative and the write entrypoint/action 406 is invoked with the database action occurring at step424 to write the new information to the transactional database 152 and,if successful, the FileOS write action for the data at step 440. If thefile write is successful, the evaluation at step 456 as to whether ornot the action is a copy read is answered in the negative as is theevaluation of the transaction as to whether or not is a copy transactionexecuted under the move action at step 468. The resources are thencommitted, temporary resources are released, and the success indicationis returned at step 484.

Consequently, for a copy transaction 402, the loop is first made throughthe read function 404 and then the write function 406. For the moveaction at entry point 410, a copy transaction is first executed with thetwo-loop operation as set forth previously. Upon completion of the copyaction, the delete action 408 is implemented in order to erase theoriginal file and its file data. Upon the third loop through the deletestep 408, the transaction is neither a read under the copy command atstep 456 nor a copy under the move command at step 468. Consequently,the move function has successfully completed, the system resources arecommitted at step 480, and a success indicator is returned at step 484.

In FIG. 5, an overview of the Java® architecture of the X:Drive system100 of the present invention is shown. The Java® architecture 500 shownin FIG. 5 may generally arise from the client 102. A file actioncontainer 504 has certain attributes and operations as do the otherbeans of the architecture 500. Contained within the file actioncontainer 504 are a number of stateful, stateless, and entity beans, aswell as other containers having other beans. The file action container504 contains two stateful beans: a user date stateful bean 506 and aprocess request stateful bean 508. The user data stateful bean 506 has auser info entity bean 510 and a security stateless bean 512.

The process request stateful bean 508 contains a single container, theXDFile container 520. The XDFile container 520 contains three (3) beansand a container. The three beans of the XDFile container 520 are: adatabase IO stateful bean 522, a file IO stateful bean 524, and an adminstateful bean 526. The container is a recovery container 530 whichcontains a recovery IO stateful bean 532, a mount status stateful bean534, a recovery admin stateful bean 536, and a recovery process statefulbean 538.

As indicated by the nature of the beans carried by the containers,stateful beans generally carry information about the state of the bean,process, or otherwise as useful information for the ends and operationsof the X:Drive system 100 of the present invention. Stateless beansgenerally carry no state information, and entity beans are generally forinformation or identification only. As Java® beans are objects intendedto carry both data and processes in association with one another, it isup to the operations of the X:Drive system 100 of the present inventionto selectively and appropriately activate the beans and enable theproper actions to take place. The file action container 504 is shown inalternative representation in FIG. 6. In FIG. 6, a client 102 issues auser authentication request 602 and an operation request 604. The userauthentication request 602 is passed into the user data stateful bean506 in the file action container 504. The operation request 604 ispassed into the process request stateful bean 508. The user informationentity bean 510 then transmits information to a user informationdatabase 610, as does the security stateless bean 512. The processrequest stateful bean uses a first property file 612 that is loaded upondeployment of the XDFile container 520. The property file is loaded intothe admin stateful bean 526 for use with the OS file system 204. A Java®transaction server 620 may operate in conjunction with the database 152as well as the OS file system 204 in order to process the operationrequest 604. The second property file 630 may be loaded by the recoveryadmin stateful bean 536 upon the bean's deployment. The recovery IOstateful bean 532 and the recovery admin stateful bean 536 both transmitinformation to the recovery queue storage buffer 640. The mount statusbean 534 operates in conjunction with the mount status of the system650.

The recovery container 530 is called when once a failed resource beginsto recover. Further description of the recovery process is given below.However, FIGS. 5 and 6 operate in tandem to show linearly (FIG. 5) andorganically (FIG. 6) the structure and operation of the XDFile object210.

FIG. 7 shows the detail of the XDFile database component. A transactionprocessor (such as Tuxedo from BEA) works in conjunction with thedatabase transaction object 214 as well as the FileIO object 212 toprovide a robust and reliable system. Both the database transaction 214and the FileIO 212 objects include logic and/or programming to handlesituations where database or disk array access cannot be guaranteed. Thedatabase.transaction object 214 handles the inherent doubt present inthe system by using replicated or repeated clusters of databases. Thereplication process creates latency or delay, in the system. In order toaccommodate this latency, the database transaction object 214 uses asession object (a data construct representing a user session on theX:Drive system 100) to determine if the user's request can betransferred, or replicated, from one database cluster to another, incase of future system failure.

An important aspect with respect to the reliable operation of theX:Drive system 100 is the need to separate databases into functionalgroups. While the query database may be optimized for quick and smallqueries and while a transaction database might be optimized for fewer,larger, more time consuming updates, the database layer 236 in theX:Drive system 100 allows for associating SQL commands with differentdatabase clusters based on functionality. Additionally, the X:Drivedatabase layer 236 is configured for consolidation and addition ofdatabases on the fly.

As shown in FIG. 7, the SQL command 710 is issued and passed to a SQLcommand evaluator 712. A SQL evaluator determines the SQL type so thatthe SQL can be sent to the appropriate database type (that is, in theX:Drive system 100, the transaction database 150, the query database152, or both).

Upon determining the database type of the SQL statement 712, thedatabase preference is evaluated at step 714 to determine if the usershould be sent back to the same database. If the user is not to be sentback to the same database, the database currently bearing the least loadis found in step 716, and query is then made in step 718 to ensure thatthe selected least-loaded database is still up, running, and available.If it is, a specification regarding the pooling of database resources iscreated 720 and transmitted to the database object 236. Database object236 then takes the SQL command and passes it to the appropriatedatabase, either the transaction database 150 or the query database 152via associated connecting pools 730.

If at step 718 the least loaded database is not available, analternative database must be used and query is made at step 736 todetermine whether or not the alternate database is up. If the alternatedatabase is not up and the evaluation step 736 fails, additionaldatabases may be queried or, as indicated in FIG. 7, a fatal error maybe generated at step 738. If the alternate database is up, a poolspecification 720 is generated and passed to the database object so thatthe SQL command may be implemented upon the transactional 152 databasesvia the connection pools 730.

If at step 714 the user must be sent back to the same database, query ismade at step 740 to determine if that database is still up. If it is,the request is passed to the pool specification 720 where it issubsequently passed to the database object 236, on to the connectionpool 730, and the appropriate database, either the transaction database150 or the query database 152. If the same database is not up and theevaluation at step 740 fails, an alternative database must be used, butthe SQL request is queried at step 744 to determine if the SQL commandis transferable to the alternate database. If not, a fatal error occursat step 746. If the SQL command is transferable, query is made at step750 to see if the alternate database is up and active. Should theevaluation fail, subsequent databases may also be queried if the SQLcommand is transferable. However, as shown in FIG. 7, if the seconddatabase is unavailable, a fatal error may be generated at 746.Otherwise, the database is up, and the evaluation at step at 750 issuccessful and the command is made available to the database object 236via the pool specification standard 720 and on to the databases throughthe connection pools 730.

In order to ensure proper operation of the XDFile database object 210, adatabase status monitor 760 persistently and on-goingly queries thedatabases 150, 152. The status is then returned to a database statusobject 762. the database status object may provide information to therecovery container 530 of the XDFile object 210.

The recovery mechanism for the X:Drive system 100 of the presentinvention is shown in FIG. 8. The FileIO object 212 uses a recoveryobject such as the recovery container 530 to handle write transactions406 (as opposed to read transactions 404) when the transaction processor214 fails. The recovery object is transparent to the user, making iteasier and more convenient for the user to use the X:Drive system 100while decreasing the concern that such a user would have in case of apower outage or other failure in one part of the X:Drive system 100.

The FileIO object 212 reports an error to the user, but informs the userthat her request was stored in the X:Drive system 100 and that theX:Drive system 100 will try to apply the change as soon as possible. Ifthe storage unit, represented as a mounting point in the EJB clusterbecomes unavailable for write transactions 406, the monitoring client760 updates the EJB network 124 that the status of the mounting point is“down.” Once the mounting point is available and checked for dataintegrity, the status is updated from “down” to “recovery” and therecovery object 530 is called to apply all queued requests for the fileaction container 504. This keeps the user from catastrophically losinguploads and other file writes, but may cause some delay in file reads.

In the recovery system 800 of the present invention, the multi-connectedpooled database object, the recovery-enabled FileIO object 212, and thetransaction processor 146 work together to create a resource layeroffering high availability, recovery, and scalability. Additionally,this resource layer (encapsulated in the XDFile EJB 210) lends itself toreplication of the data, both geographically and locally. Suchreplication preferably has the three essential traits of being off-site,application-driven, and accessible. With this level of controlledreplication, secondary X:Drive clusters are enabled in geographicallydiverse locations in order to enhance the reliability of the X:Drivesystem 100. Consequently, data loss from one data center or even thephysical loss of an entire data center would not cause loss of customerdata or access. Re-direction would occur dynamically and thisinformation would be replicated in a plurality of sites across theX:Drive system 100, the query or metadata databases provide multiplepointers to the user's data.

In the recovery system 800 of FIG. 8, the recovery system is initiallyinitiated when the MPS Bean 534 is set for a mode to detect mount pointrecovery at step 804. At step 804, a recover method is called and theexternal mount point is checked. Query is made at step 806 to evaluatewhether or not recovery is already occurring. If recovery is alreadyoccurring, an exception is thrown at step 808 and exit is made at thisfinish point. If recovery is not already occurring, a list of mountpoints in recovery mode is generated in step 810. Additionally, at step812 a list of mount points which are down is also generated. Query ismade at the evaluation step 818 as to the presence of available recoveryobjects in the recovery queue. If no such objects are available in thequeue, the disk or other database is set into the “up” mode at step 820.The queue for that disk is then unlocked in step 822, and the recoveryprocess is complete at step 824. If at evaluation step 818 recoveryobjects are still in the queue, evaluation is made as to whether or notthe system has gone past the lock count at step 830. If so, the queuefor the disk in recovery is locked at step 832 for both the lock countevaluation 830 and the queue lock 832 step, control is then directed tothe evaluation step as to whether or not the target file exists 834. Ifthe target file does not exist and the evaluation at step 834 fails, therecovery object is removed from the queue at step 840. The status of therecovery is subsequently put in the request for alert queue at step 842and return is then made to the query step 818 to determine whether ornot objects are still available for recovery in the queue.

If the target file does exist when evaluated at step 834, evaluation ismade as to whether or not the request is more current than the file atstep 850. If the request is older than the current file, the recoveryobject is removed from the queue at step 840, and the status for therequest is put in the request or alert queue 842 and control returnsback to the evaluation step 818 to see if any further recovery objectsare available in the recovery queue.

If, in evaluating the request, it is found that the request is morecurrent than the file, the request is submitted to the XDFile object 210at step 852. The submission of the request to the XDFile object 210 isnot recoverable. If the submitted request is successful as indicated bythe evaluation at step 854, the recovery object is removed from thequeue at step 840, its status is put into the request for alert queue atstep 842 and evaluation is made at step 818 as to the presence of anyadditional recovery objects in the recovery queue. However, if insubmitting the request to the XDFile object 210 at step 852 thesubmission fails, query is made at step 860 as to whether or not themount point has gone down. If at step 860 the mount point is still up,the request from this mount point is ignored at step 862 and the queuefor the disk is unlocked at step 864. Control of the program is thenreturned to the recovery object availability query in evaluation step818.

As shown in FIG. 9, the mount point status bean 534 has UP, DOWN, andRECOVERY states. This bean is applicable to the file database 150, aswell as user disks 970, 972 as well as recovery disks 974, 976.Additionally, the recovery admin stateful bean 536 is directed towardsthe recovery database 980 in order to effect the recovery process 800.

In order to effect virus scanning and repair features, the X:Drivesystem 100 preferably uses the Java® JNI (Java Native Interface) toaccess a Norton Anti-Virus or other dynamically linked library (NAV.DLL)to scan files for viruses via a Java® servlet. The Java® servlet runs ona Windows™ version X server and can use JNI to make calls to the NAV.DLLdynamically linked libraries. In effect, the Windows™ X machine becomesa specialized NAV.DLL server located at the EJB network layer 124 of theX:Drive system 100, on a sub-network of the resource network. The logicintegrating the NAV.DLL dynamic linked libraries with all X:Drive filewrites is shown schematically in the flow diagram in FIG. 10.

As shown in FIG. 10, the virus scanning sub-system 1000 takes thefile/transaction ID 1002 and a transaction ID 1004 from a user 1006. Thefile/transaction ID 1002 is passed to a file write process 1008 executedby a SUN® or other web server 1010. The file is written to both thedatabase generically indicated at reference 1020 and to a temporary filestorage area 1022. The file write process 1008 passes the filetransaction ID to the Norton Anti-Virus (NAV) process 1024. Within theNAV process 1024 is NAV scanner 1026. The NAV scantier monitors the datastream or otherwise to determine and detect the presence of any viruses.If upon evaluation the NAV process 1024 detects a virus at evaluationstep 1028, data sink action is taken with respect to the database 1020.If no virus is detected, the sequence moves to its final termination atstep 1030 and data sink action is taken with respect to a temporary fileon medium 1032.

While both the file and transaction ID 1002 are delivered to the filewrite process 1008, the transaction ID alone 1004 is transmitted to afetch location info step 1040 on a SUN® or other web server 1010. Thefetch location info step 1040 transmits its results to an evaluationstep 1042, which determines whether or not the file is in the temporarystorage area 1022. If the file is in the temporary area, the file'supload status is shown in step 1044. If the file is not in the temporarymedium 1022, virus information is fetched at step 1050 in the filestatus process 1036.

Once the virus information has been fetched, it is evaluated as towhether or not there is a virus present at step 1052. If there is novirus detected, then the virus evaluation terminates and a display ofsame may be made at step 1054.

However, if evaluation step 1052 indicates the presence of one or moreviruses, a plurality of virus options may be shown and presented to theuser at step 1060. Among the virus options available are: the cleaningof the virus at step 1062, moving the virus to a different location atstep 1064, and/or deleting the virus in step 1066. If step 1064 is takenwith the move of the virus-laden file despite its infectious nature ismade, movement of the file with its final destination is made in step1070.

As shown in FIG. 10, a number of data sink actions are taken withrespect to information. Additionally, as indicated by FIG. 10, the NAVprocess 1024 is a separate entity and may be considered to be a JAVA®servlet/daemon living on specialized Windows® NT or other servers.

In order to make resources available on an on-going basis to the virusscanning sub-system 1000 of the present invention, a chron file 1074 (afile executing commands on a periodic basis according to the time) isused to remove old files from a first temporary storage resource 1002.

FIG. 11 shows the Skip the Download/Save to My Xdrive system where afile on the Internet can be transferred over to an individual's X:Driveat generally data speeds far faster than those available to the enduser. This allows the user to exercise dominion and control over thefile without having to bear the burden of downloading it to the localcomputer at the present moment. Once the transfer has taken place acrossthe Internet from the host to the X:Drive system 100, then the user maydownload the file stored in his X:Drive directory to his local computerat his convenience.

As X:Drive exists on the Internet network, transferring a file from onenetwork resource (such as a web or FTP server) to the user's X:Drive ismade much faster from the user's standpoint by by-passing the localconnection to the user and allowing the user to submit the transferrequest directly to the X:Drive network for execution. The X:Drivesystem 100 then downloads the requested data from the target server tothe user's X:Drive over the presumably higher speed connections of thepublic Internet.

As shown in FIG. 11, the Save to My Xdrive system 1100 first has theuser 1110 submit the URL at step 1112. In order to access the X:Drivesystem 100 of the present invention, the user submits the URL as well ashis or her user name and password at step 1114. Upon submitting the URLand the appropriate verification information, evaluation is made of theinformation for authentication purposes at step 1116. If the evaluationfails and authentication is not achieved, a login form is displayed inconjunction with the previously-indicated URL at step 1118. If therequest is authenticated, it is submitted to the STD/STMX (Skip theDownload/Save to My Xdrive) queue 1132 at step 1130. A status process isthen spawned at step 1134.

Save to My Xdrive status is then checked on an on-going basis by usingthe queue in the temporary storage area at step 1136. Query is made asto whether or not the transfer is complete at step 1140. If the transferis complete at step 1140, then the successful completion is indicated tothe user at step 1142. However, if the transfer is not complete, queryis made as to the presence of any transfer errors at step 1146. If anerror has occurred, an error message is displayed to the user at step1148. However, if the transfer is incomplete but no errors haveoccurred, the same is then displayed to the user at step 1150, and ashort pause is taken at step 1152 for re-invoking the check STD processat step 1136.

Once the STD queue 1132 receives the request, a daemon process processesthe request from the STD queue at step 1160. Query is made as to thebusiness logic of the queued request at step 1162. If the request failsthe business logic check 1162, the status is updated at step 1164.Control may transfer back to the STD queue 1132.

If the business logic check succeeds at step 1162, the URL site iscontacted by the X:Drive system 100 at step 1170 and the downloadprocess is activated. The data transmitted by the URL is then saved intemporary, X:Drive space in step 1172, with the data being transferredthen to the user data space at step 1174. The URL site 1180 may existanywhere on the Internet so long as it is available to the X:Drivesystem 100. In a similar manner, a temporary storage space 1182 may alsoexist anywhere on the Internet so long as it is accessible andcontrollable by the X:Drive system 100.

Upon transferring data to the user's data space as shown in step 1174,query is made as to the success of the transfer at step 1188. For eithersuccess or failure of the successful file transfer at evaluation step1188, the status is updated at step 1164 and is passed on to the STDqueue 1132 until either success or an error is finally achieved. Thestatus process spawned at step 1130 monitors the update status generatedby step 1164 and displays the status to the user during and after thedownload of the file from the Internet to the user's X:Drive system.

FIG. 12 shows a schematic and flowchart diagram for the client systemgenerally used under Microsoft® Windows™ for achieving the presentinvention. The X:Drive system offers its clients two basic services: afile access service by which files can be uploaded and downloaded to andfrom X:Drive, as well as a file manipulation service from which filemetadata can be obtained and manipulated. Both of these services relyupon the context of their usage. For example, the web client of thepresent invention uses native upload and download features as well asdialogs in the user's web browsers to facilitate the service.

With the use of the web browsers on the local machine, Windows® Xclients use the Windows™ TCP/IP stacks inherently present with theWindows® version X operating system. All the file transfers effected bythe X:Drive system can take place as HTTP POST/GET or, preferably,Web-DAV transfers. Generally, two basic layers are present in the filemanipulation servers of the X:Drive system 100 of the present invention.An XML parser operates in conjunction with an XML data displayer. Bycoordinating the two basic layers of the file manipulation service, theserver is able to respond with generally the same XML code to allclients. The client is then responsible for converting the XML to arelevant data structure and displaying the XML in an appropriatecontext. In the present invention, the JavaScript web client receivesthe XML code and parses it into a JavaScript data structure. A displaylayer in association with the client and/or browser renders the datastructure as an HTML document. The Windows® X client parses the same XMLcode, but the display layer renders the data structure into a devicelisting that is understood by the Windows® version X operating system.The importance of this layered architecture is that it generally makestrivial the creation of new clients. Instead of simply creating dynamicweb pages (and thus limiting service to web browsers alone), the X:Drivesystem 104) can enable many platforms, such as operating systems,without altering the server structure. Most platforms come with somesort of XML parsing layers, and many platforms come with display layersready made. Consequently, the time to market may generally be consideredlow and efficient establishment and implementation of the X:Drive system100 of the present invention can be achieved fairly quickly.Additionally, expansion into new platforms generally becomes muchquicker as no alteration of the server structure generally needs tooccur as Java® and related program functionalities are highly portablefrom one system to another.

In the client system 1200, as shown in FIG. 12, the client 102 has afile access service 1202, including a request processing layer 1204coupled to a network I/O layer 1206. Commands and data are thentransmitted to the server side of the X:Drive system 100 where theserver side request processing layer 1210 transmits the data to a queryevaluating whether or not the request is one for metadata at step 1212.If the evaluation fails and the request is not one for metadata, thenetwork I/O layer 1216 and the resource access layer 1218 are invoked inorder to provide access to and operation of the transaction database152.

If the request for metadata query at step 1212 succeeds, the request ispassed on to the resource access layer 1218 and on to the XML generationlayer 1220. The response to the request from the metadatabase 150 istransmitted to the file manipulation service system 1230 of the client120. The XML transmitted by the XML generation layer 1220 is received bythe file manipulation service 1230 as well as its XML handler 1232. TheXML is then passed on to the XML parser layer at step 1234 to arrive ata data structure 1236 that is then ready for display and so is passed onto the data display layer 1238 for display to the user who may thenre-initiate the process by implementing the file access service 1202.

FIG. 13 shows the X:Drive system 100 as implemented on a Windows™ Xmachine, in this case, a Windows '98 machine (an Intel-based personalcomputer running the Microsoft Windows '98 operating system).

The second frontmost window 1310 of FIG. 13 is headed by the inscription“My Computer” and shows the presence of a drive at logical letter X:1312 with the X:Drive logo and the label www.xdrive.com (X:). This is anexample of the user interface provided by the client application. TheX:Drive system is transparent to the user and functions as any otherdrive present on the system.

If the user were to click on or activate the X:\ drive on the MyComputer window 1310, the second window 1320 appears (partiallyobscuring the “My Computer” window 1310) and shows the listing under theX:\ Drive. The address of the window 1320 shows the location of thedirectory as being at X:\ 1322.

Also shown in FIG. 13 is the desktop icon 1330, the start menu icon1336, and the system tray icon 1340. These icons accompany the clientprogram 102 and provide greater functionality for the user. Each iconserves to activate the client program in accordance with user-settablepreferences.

FIG. 13 also shows the web-based application 1350 in the background,behind the My Computer 1310 and X:\ 1320 windows. The web-basedapplication window 1350 is shown in FIG. 14. Note should be taken of theexact correspondence between the directory structures of web-basedapplication window 1350 and the client-based application window 1320.This correspondence provides the user with a uniform, familiar, anddependable interface upon with the user can rely.

As set forth above, the three accompanying Appendices are incorporatedherein in their entirety, as is the previously filed provisionalapplication.

While the present invention has been described with regards toparticular embodiments, it is recognized that additional variations ofthe present invention may be devised without departing from theinventive concept.

1-24. (canceled)
 25. A computer-implemented method comprising thefollowing operations performed by at least one processor: receiving,from a client system, a request to transfer a first file stored on ahost server to a database system, wherein the transfer request istransmitted to a proxy server for isolating the transfer request, andwherein the transfer request includes an identifier that identifies thefirst file and an identifier of a user of the client system;transferring, using a communications network, the first file from thehost server to the database system, the database system configured tostore the first file in a storage area allocated to the identified userof the client system; receiving, from the client system, a request toaccess the first file stored on the database system, the request toaccess the first file including authentication data associated with theuser; verifying the authenticating data associated with the user; andpermitting, in response to verifying the user, the client system toaccess the first file stored on the database system.
 26. Thecomputer-implemented method of claim 25, wherein the authentication dataassociated with the user comprises a user name and password.
 27. Thecomputer-implemented method of claim 25, wherein the identifier thatidentifies the first file specifies a location of the first file. 28.The computer-implemented method of claim 25, further comprising theoperations of: monitoring a status of the transfer request; andreporting the status to the user.
 29. The computer-implemented method ofclaim 28, wherein the status is at least one of complete, incomplete,and transfer error.
 30. The computer-implemented method of claim 25,wherein permitting the client system to access the first file furthercomprises: permitting the user to download the first file stored on thedatabase system to the client system.
 31. The computer-implementedmethod of claim 25, wherein permitting the client system to access thefirst file further comprises: permitting the user to share the firstfile stored on the database system with other users.
 32. Thecomputer-implemented method of claim 25, wherein the first file istransferred from the host server to the database system using a fastertransfer speed than that provided by a direct transfer from the hostserver to the client system.
 33. An apparatus comprising: at least oneprocessor; and a storage device comprising instructions that, whenexecuted by the at least one processor, cause the at least one processorto perform the following operations: receiving, from a client system, arequest to transfer a first file stored on a host server to a databasesystem, wherein the transfer request is transmitted to a proxy serverfor isolating the transfer request, and wherein the transfer requestincludes an identifier that identifies the first file and an identifierof a user of the client system; transferring, using a communicationsnetwork, the first file from the host server to the database system, thedatabase system configured to store the first file in a storage areaallocated to the identified user of the client system; receiving, fromthe client system, a request to access the first file stored on thedatabase system, the request to access the first file includingauthentication data associated with the user; verifying theauthenticating data associated the user; and permitting, in response toverifying the user, the client system to access the first file stored onthe database system.
 34. The apparatus of claim 33, wherein theauthentication data associated with the user comprises a user name andpassword.
 35. The apparatus of claim 33, wherein the identifier thatidentifies the first file specifies a location of the first file. 36.The apparatus of claim 33, wherein the at least one processor furtherperforms the following operation: monitoring a status of the transferrequest; and reporting the status to the user.
 37. The apparatus ofclaim 36, wherein the status is at least one of complete, incomplete,and transfer error.
 38. The apparatus of claim 33, wherein permittingthe client system to access the first file further comprises: permittingthe user to download the first file stored on the database system to theclient system.
 39. The apparatus of claim 33, wherein permitting theclient system to access the first file further comprises: permitting theuser to share the first file stored on the database system with otherusers.
 40. The apparatus of claim 33, wherein the first file istransferred from the host server to the database system using a fastertransfer speed than that provided by a direct transfer from the hostserver to the client system.
 41. A tangible, non-transitorycomputer-readable medium storing instructions that, when executed by atleast one processor, cause the at least one processor to performoperations comprising: receiving, from a client system, a request totransfer a first file stored on a host server to a database system,wherein the transfer request is transmitted to a proxy server forisolating the transfer request, and wherein the transfer requestincludes an identifier that identifies the first file and an identifierof a user of the client system; transferring, using a communicationsnetwork, the first file from the host server to the database system, thedatabase system configured to store the first file in a storage areaallocated to the identified user of the client system; receiving, fromthe client system, a request to access the first file stored on thedatabase system, the request to access the first file includingauthentication data associated with the user; verifying theauthenticating data associated the user; and permitting, in response toverifying the user, the client system to access the first file stored onthe database system.
 42. The medium of claim 41, wherein theauthentication data associated with the user comprises a user name andpassword.
 43. The medium of claim 41, wherein the instructions furthercause the at least one processor to perform operations comprising:monitoring a status of the transfer request; and reporting the status tothe user.
 44. The medium of claim 43, wherein the status is at least oneof complete, incomplete, and transfer error.